home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19950329-19950528
/
000239_news@columbia.edu_Wed Apr 26 03:18:58 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-07-31
|
2KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA27549
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Wed, 26 Apr 1995 12:24:02 -0400
Received: by apakabar.cc.columbia.edu id AA24781
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Wed, 26 Apr 1995 12:23:59 -0400
Path: news.columbia.edu!sol.ctr.columbia.edu!news.kei.com!news.mathworks.com!udel!gatech!swrinde!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: kermit script suspends with escape
Message-Id: <1995Apr26.091858.48723@cc.usu.edu>
Date: 26 Apr 95 09:18:58 MDT
References: <EGORMAN.95Apr24171009@dev27>
Followup-To: comp.protocols.kermit.misc
Organization: Utah State University
Lines: 27
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <EGORMAN.95Apr24171009@dev27>, egorman@dev27 (Eugene Gorman) writes:
>
> I have created a dialup kermit script that will suspend on the
> appearance of an escape (ie ^[). The site I connect to sends out and
> escape right after the CONNECT message, and my kermit script stops.
> If I hit return at this point, the script will continue and work just
> fine. I am trying to run this without human intervention. Is there a
> way to tell the kermit script to ignore escapes? If I run this by
> hand, I am not suspended.
---------
I think I understand your situation, and the cure too.
The problem is the remote host sends some bytes during the
Connect process, and the last of them is ESC. At that point your script
halts and you need to intervene to continue.
Here's my guess. You are echoing arriving material to the screen
and ANSI.SYS is loaded. ANSI.SYS is trying to "parse" (recognize) control
sequences and it got the lead-in, ESC, for one. Thus it sits there waiting
for more of the sequence before displaying more text. It's running, but
we can't see that. The script is running, but ANSI.SYS has suspended screen
updates until a control-sequence terminator (typically a letter) has
arrived.
My suggestions are
a) turn off script echoing (SET INPUT ECHO OFF) through the ESC,
or b) match on material up to or well after the ESC. I think the ESC
is part of a control sequence sent to you and it's best to let Kermit's
terminal emulator deal with it.
Joe D.